Automatically determining a size for a content item for a web page

ABSTRACT

Systems and methods for automatically determining a content item size may be based on a size of a viewport and a width of a parent element. A script may be configured to determine a size of a viewport, determine a width of a parent element of a resource, and determine a content item size based, at least in part, on the size of the view port and the width of the parent element. A dimension of the determined content item size may be used by a content item selection system to determine a set of content items. A content item selection system may select a content item from the determined set of content items and serve data to effect display of the selected content item in the parent element with the resource.

CROSS-REFERENCE TO RELATED PATENT APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.14/048,921, filed Oct. 8, 2013 entitled, “Automatically Determining ASize For A Content Item For A Web Page”, the subject matter of which ishereby incorporated by reference, which claims the benefit of U.S.Provisional Application No. 61/884,822, entitled “AutomaticallyDetermining a Size for a Content Item for a Web Page,” filed Sep. 30,2013, the disclosure of which is incorporated by reference herein in itsentirety.

BACKGROUND

In a networked environment, such as the Internet or other networks,first-party content providers can provide information for publicpresentation on resources, for example web pages, documents,applications, and/or other resources. The first-party content caninclude text, video, and/or audio information provided by thefirst-party content providers via, for example, a resource server forpresentation on a client device over the Internet. Additionalthird-party content can also be provided by third-party contentproviders for presentation on the client device together with thefirst-party content provided by the first-party content providers. Thus,a person viewing a resource can access the first-party content that isthe subject of the resource, as well as the third-party content that mayor may not be related to the subject matter of the resource.

SUMMARY

One implementation relates to a method for selecting and serving acontent item based on a determined content item size for a resource. Themethod may include serving a script to a client device in response to arequest. The script may be configured to determine a size of a viewport,determine a width of a parent element of a resource, and determine acontent item size based, at least in part, on the size of the view portand the width of the parent element. The method may further includereceiving a dimension of the determined content item size anddetermining a set of content items based, at least in part, on thereceived dimension of the determined content item size. The methodfurther includes selecting a content item from the determined set ofcontent items and serving data to effect display of the selected contentitem in the parent element with the resource.

Another implementation relates to a system for serving content itemsthat includes one or more processing modules and one or more storagedevices storing instructions that, when executed by the one or moreprocessing modules, cause the one or more processing modules to performseveral operations. The operations may include serving a script to aclient device in response to a request. The script may be configured todetermine a size of a viewport, determine a width of a parent element ofa resource, rank each predetermined standard size of a set ofpredetermined standard sizes based, at least in part, on the size of theviewport and the width of the parent element, and determine a contentitem size based on the ranking of each predetermined standard size ofthe set of predetermined sizes. The operations may further includereceiving a dimension of the determined content item size anddetermining a set of content items based, at least in part, on thereceived dimension of the determined content item size. The operationsfurther include selecting a content item from the determined set ofcontent items and serving data to effect display of the selected contentitem in the parent element with the resource.

Yet another implementation relates to a computer-readable storage devicestoring instructions that, when executed by one or more processingmodules, cause the one or more processing modules to perform severaloperations. The operations include serving a script to a client devicein response to a request. The script may be configured to determine asize of a viewport, determine a width of a parent element of a resource,rank each predetermined standard size of a set of predetermined standardsizes based, at least in part, on an area of each predetermined standardsize and a ratio match value, and determine a content item size based onthe ranking of each predetermined standard size of the set ofpredetermined sizes. The operations may further include receiving adimension of the determined content item size and determining a set ofcontent items based, at least in part, on the received dimension of thedetermined content item size. The operations further include selecting acontent item from the determined set of content items and serving datato effect display of the selected content item in the parent elementwith the resource.

BRIEF DESCRIPTION OF THE DRAWINGS

The details of one or more implementations are set forth in theaccompanying drawings and the description below. Other features,aspects, and advantages of the disclosure will become apparent from thedescription, the drawings, and the claims, in which:

FIG. 1 is a block diagram depicting an implementation of a system forproviding information via a network;

FIG. 2A is an illustration of an implementation of a first-partyresource having third-party content shown in a window of a browser;

FIG. 2B is an illustration of the implementation of the first-partyresource having third-party content of FIG. 2A shown with the window ofthe browser resized;

FIG. 3A is an illustration of an implementation of another first-partyresource displayed on a mobile device and having third-party content;

FIG. 3B is an illustration of the implementation of the first-partyresource displayed on the mobile device of FIG. 3A shown displayed afterthe mobile device is rotated;

FIG. 4 is an illustration of an implementation of a first-party resourcehaving multiple divisions and showing an example third-party contentitem in a parent element;

FIG. 5A is an illustration of an implementation of a first-partyresource having multiple divisions and showing an example third-partycontent item in a parent element;

FIG. 5B is an illustration of the first-party resource of FIG. 5Ashowing the example third-party content item rotated relative to thefirst-party resource;

FIG. 6 is a flow diagram of an implementation of a process toautomatically determine a size for a content item based on a parentelement of the content item slot;

FIG. 7 is a flow diagram of an implementation of a process to select andserve a content item based on an automatic determination of a size forthe content item; and

FIG. 8 is a is a block diagram illustrating a general architecture for acomputer system that may be employed to implement various elements ofthe systems and methods described and illustrated herein.

It will be recognized that some or all of the figures are schematicrepresentations for purposes of illustration. The figures are providedfor the purpose of illustrating one or more embodiments with theexplicit understanding that they will not be used to limit the scope orthe meaning of the claims.

DETAILED DESCRIPTION

Following below are more detailed descriptions of various conceptsrelated to, and implementations of, methods, apparatuses, and systemsfor providing information on a computer network. The various conceptsintroduced above and discussed in greater detail below may beimplemented in any of numerous ways, as the described concepts are notlimited to any particular manner of implementation. Examples of specificimplementations and applications are provided primarily for illustrativepurposes.

A computing device (e.g., a client device) can view a resource, such asa web page, via the Internet by communicating with a server, such as aweb page server, corresponding to that resource. The resource includesfirst-party content that is the subject of the resource from afirst-party content provider, as well as additional third-party providedcontent, such as advertisements or other content. Website visitors use awide range of devices with a wide range of screen sizes for viewing webpages. Accordingly, the presentation of the resource may be modifiedbased on the type of device requesting the resource (e.g., a desktopcomputer, a tablet computer, a mobile device, etc.), a screen size ofthe device requesting the resource, and/or a viewable size of thefirst-party content on the client device. Such responsive web designenables the resource to be displayed in an aesthetically pleasing mannerto an end user based on the client device and/or how the first-partycontent is being displayed on the client device. In someimplementations, website owners manually decide what sizes ofthird-party content items they want for to be displayed with their webpages. That is, the presentation of third-party content items may bespecified for the different types of devices requesting the resource,the different screen sizes, and/or the different viewable sizes of thefirst-party content such that the third-party content item does notdominate the viewable area of the device, yet is not overly smallrelative to the first-party content of the resource. For example, alarge third-party content item that looks good and converts well on alarge desktop screen may be too large on a mobile device. Conversely, athird-party content item that is of a small size, such as 320 pixels(px) by 50 pixels, designed to be presented on small displays of mobiledevices may not be noticeable on a large desktop screen. Thus, it may beuseful to automatically determine the size for a content item to bepresented with the resource and to select and serve a third-partycontent item based on the determined size, as will be described ingreater detail herein.

The selection and serving of the third-party content item may be inresponse to a request to access a web page from a web page server and/ora client device that communicates with a data processing system, such asa content item selection system, to request a content item to bepresented with the requested web page. The content item selection systemcan select a third-party content item and provide data to effectpresentation of the content item with the requested web page on adisplay of the client device. In some instances, the content item isselected and served with a resource associated with a search query. Forexample, a search engine may return search results on a search resultsweb page and may include third-party content items related to the searchquery in one or more content item slots of the search results web page.

In some instances, a device identifier is associated with the clientdevice. The device identifier may include a randomized number associatedwith the client device to identify the device during subsequent requestsfor resources and/or content items. In some instances, the deviceidentifier is configured to store and/or cause the client device totransmit information related to the client device to the content itemselection system and/or resource server (e.g., a web browser type, anoperating system, prior resource requests, prior content item requests,etc.).

In situations in which the systems discussed here collect personalinformation about users, or may make use of personal information, theusers may be provided with an opportunity to control whether programs orfeatures collect user information (e.g., information about a user'ssocial network, social actions or activities, profession, a user'spreferences, or a user's current location), or to control whether and/orhow to receive content from the content server that may be more relevantto the user. In addition, certain data may be treated in one or moreways before it is stored or used, so that personally identifiableinformation is removed. For example, a user's identity may be treated sothat no personally identifiable information can be determined for theuser, or a user's geographic location may be generalized where locationinformation is obtained (such as to a city, ZIP code, or state level),so that a particular location of a user cannot be determined. Thus, theuser may have control over how information is collected about the userand used by a content server.

A third-party content provider, when providing third-party content itemsfor presentation with requested resources via the Internet or othernetwork, may utilize a content item management service to control orotherwise influence the selection and serving of the third-party contentitems. For instance, a third-party content provider may specifyselection criteria (such as keywords) and corresponding bid values thatare used in the selection of the third-party content items. The bidvalues may be utilized by the content item selection system in anauction to select and serve content items for display with a resource.For example, a third-party content provider may place a bid in theauction that corresponds to an agreement to pay a certain amount ofmoney if a user interacts with the provider's content item (e.g., theprovider agrees to pay $3 if a user clicks on the provider's contentitem). In other implementations, a third-party content provider mayplace a bid in the auction that corresponds to an agreement to pay acertain amount of money if the content item is selected and served(e.g., the provider agrees to pay $0.005 each time a content item isselected and served). In some instances, the content item selectionsystem uses content item interaction data to determine the performanceof the third-party content provider's content items. For example, usersmay be more inclined to click on third-party content items on certainweb pages over others. Accordingly, auction bids to place thethird-party content items may be higher for high-performing web pages,categories of web pages, and/or other criteria, while the bids may belower for low-performing web pages, categories of web pages, and/orother criteria.

In some instances, a web page or other resource (such as, for example,an application) includes one or more content item slots or units inwhich a selected and served third-party content item may be displayed.The code (e.g., JavaScript®, HTML, etc.) defining a content item slotfor a web page or other resource may include instructions to request athird-party content item from the content item selection system to bedisplayed with the web page. Such code may be executed by the clientdevice to perform other tasks prior to requesting the third-partycontent item. For example, the code may be configured to automaticallydetermine the size for a content item to be presented with the resourcebased on a type of the client device, a screen size of the clientdevice, a viewable size of the first-party content on the client device,and/or the size of a parent element to the content item slot or unit ofthe resource such that the request sent to the content item selectionsystem results in an appropriately sized content item for the resourcepresented on the display of the client device. Such responsive contentitem slots or units provide first-party content providers with an easysolution and implementation for presenting third-party content itemswithout having to manually define the sizes for content items for thevarious sizes that the first-party content may be displayed at.

While the foregoing has provided an overview of a content item selectionsystem that can automatically determine a size for a content item, morespecific implementations and methods for such a system will now bedescribed.

FIG. 1 is a block diagram of an implementation of a system 100 forproviding information via at least one computer network such as thenetwork 106. The network 106 may include a local area network (LAN),wide area network (WAN), a telephone network, such as the PublicSwitched Telephone Network (PSTN), a wireless link, an intranet, theInternet, or combinations thereof. The system 100 can also include atleast one data processing system or processing module, such as a contentitem selection system 108. The content item selection system 108 caninclude at least one logic device, such as a computing device having aprocessing module, to communicate via the network 106, for example witha resource server 104, a client device 110, and/or a third-party contentserver 102. The content item selection system 108 can include one ormore data processors, such as a content placement processor, configuredto execute instructions stored in a memory device to perform one or moreoperations described herein. In other words, the one or more dataprocessors and the memory device of the content item selection system108 may form a processing module. The data processor may include amicroprocessor, an application-specific integrated circuit (ASIC), afield-programmable gate array (FPGA), etc., or combinations thereof. Thememory may include, but is not limited to, electronic, optical,magnetic, or any other storage or transmission device capable ofproviding processor with program instructions. The memory may include afloppy disk, compact disc read-only memory (CD-ROM), digital versatiledisc (DVD), magnetic disk, memory chip, read-only memory (ROM),random-access memory (RAM), Electrically Erasable Programmable Read-OnlyMemory (EEPROM), erasable programmable read only memory (EPROM), flashmemory, optical media, or any other suitable memory from which processorcan read instructions. The instructions may include code from anysuitable computer programming language such as, but not limited to,ActionScript®, C, C++, C#, HTML, Java®, JavaScript®, Perl®, Python®,Visual Basic®, and XML. The processing module may process instructionsand output data to effect presentation of one or more content items tothe resource server 104 and/or the client device 110. In addition to theprocessing module, the content item selection system 108 may include oneor more databases configured to store data. The content item selectionsystem 108 may also include an interface configured to receive data viathe network 106 and to provide data from the content item selectionsystem 108 to any of the other devices on the network 106. The contentitem selection system 108 can include a server, such as an advertisementserver or otherwise.

The client device 110 can include one or more devices such as acomputer, laptop, desktop, smart phone, tablet, personal digitalassistant, set-top box for a television set, a smart television, orserver device configured to communicate with other devices via thenetwork 106. The device may be any form of portable electronic devicethat includes a data processor and a memory, i.e., a processing module.The memory may store machine instructions that, when executed by aprocessor, cause the processor to perform one or more of the operationsdescribed herein. The memory may also store data to effect presentationof one or more resources, content items, etc. on the computing device.The processor may include a microprocessor, an application-specificintegrated circuit (ASIC), a field-programmable gate array (FPGA), etc.,or combinations thereof. The memory may include, but is not limited to,electronic, optical, magnetic, or any other storage or transmissiondevice capable of providing processor with program instructions. Thememory may include a floppy disk, compact disc read-only memory(CD-ROM), digital versatile disc (DVD), magnetic disk, memory chip,read-only memory (ROM), random-access memory (RAM), ElectricallyErasable Programmable Read-Only Memory (EEPROM), erasable programmableread only memory (EPROM), flash memory, optical media, or any othersuitable memory from which processor can read instructions. Theinstructions may include code from any suitable computer programminglanguage such as, but not limited to, ActionScript®, C, C++, C#, Java®,ActionScript®, JavaScript®, JSON, Perl®, HTML, HTML5, XML, Python®, andVisual Basic®.

The client device 110 can execute a software application (e.g., a webbrowser or other application) to retrieve content from other computingdevices over network 106. Such an application may be configured toretrieve first-party content from a resource server 104. In some cases,an application running on the client device 110 may itself befirst-party content (e.g., a game, a media player, etc.). In oneimplementation, the client device 110 may execute a web browserapplication which provides a browser window on a display of the clientdevice. The web browser application that provides the browser window mayoperate by receiving input of a uniform resource locator (URL), such asa web address, from an input device (e.g., a pointing device, akeyboard, a touch screen, or another form of input device). In response,one or more processors of the client device executing the instructionsfrom the web browser application may request data from another deviceconnected to the network 106 referred to by the URL address (e.g., aresource server 104). The other device may then provide webpage dataand/or other data to the client device 110, which causes visual indiciato be displayed by the display of the client device 110. Accordingly,the browser window displays the retrieved first-party content, such aswebpages from various websites, to facilitate user interaction with thefirst-party content.

The resource server 104 can include a computing device, such as aserver, configured to host a resource, such as a webpage or otherresource (e.g., articles, comment threads, music, video, graphics,search results, information feeds, etc.). The resource server 104 may bea computer server (e.g., a file transfer protocol (FTP) server, filesharing server, web server, etc.) or a combination of servers (e.g., adata center, a cloud computing platform, etc.). The resource server 104can provide resource data or other content (e.g., text documents, PDFfiles, and other forms of electronic documents) to the client device110. In one implementation, the client device 110 can access theresource server 104 via the network 106 to request data to effectpresentation of a resource of the resource server 104.

One or more third-party content providers may have third-party contentservers 102 to directly or indirectly provide data for third-partycontent items to the content item selection system 108 and/or to othercomputing devices via network 106. The content items may be in anyformat that may be presented on a display of a client device 110, forexample, graphical, text, image, audio, video, etc. The content itemsmay also be a combination (hybrid) of the formats. The content items maybe banner content items, interstitial content items, pop-up contentitems, rich media content items, hybrid content items, etc. The contentitems may also include embedded information such as hyperlinks,metadata, links, machine-executable instructions, annotations, etc. Insome instances, the third-party content servers 102 may be integratedinto the content item selection system 108 and/or the data for thethird-party content items may be stored in a database of the contentitem selection system 108.

In one implementation, the content item selection system 108 canreceive, via the network 106, a request for a content item to presentwith a resource. The received request may be received from a resourceserver 104, a client device 110, and/or any other computing device. Theresource server 104 may be owned or ran by a first-party contentprovider that may include instructions for the content item selectionsystem 108 to provide third-party content items with one or moreresources of the first-party content provider on the resource server104. In one implementation, the resource may include a webpage. Theclient device 110 may be a computing device operated by a user(represented by a device identifier), which, when accessing a resourceof the resource server 104, can make a request to the content itemselection system 108 for one or more content items to be presented withthe resource, for instance. The content item request can includerequesting device information (e.g., a web browser type, an operatingsystem type, one or more previous resource requests from the requestingdevice, one or more previous content items received by the requestingdevice, a language setting for the requesting device, a geographicallocation of the requesting device, a time of a day at the requestingdevice, a day of a week at the requesting device, a day of a month atthe requesting device, a day of a year at the requesting device, etc.)and resource information (e.g., URL of the requested resource, one ormore keywords of the content of the requested resource, text of thecontent of the resource, a title of the resource, a category of theresource, a type of the resource, a property of the resource, aninteractivity level of the resource, a ranking of the resource, apopularity of the resource, a category of a publisher associated withthe resource, a type of a publisher associated with the resource, aproperty of a publisher associated with the resource, etc.). Theinformation or parameters that the content item selection system 108receives can include a HyperText Transfer Protocol (HTTP) cookie whichcontains a device identifier (e.g., a random number) that represents theclient device 110. In some implementations, the device and/or theresource information or parameters may be appended to a content itemrequest URL (e.g., /page/contentitem?devid=abc123&devnfo=A34r0). In someimplementations, the device and/or the resource information orparameters may be encoded prior to being appended the content itemrequest URL. The requesting device and/or the resource information orparameters may be utilized by the content item selection system 108 toselect third-party content items to be served with the requestedresource and presented on a display of a client device 110. In someimplementations, a height value and a width value may be included withthe content item request such that the content item selection system 108may use the height and width as part of the selection of a content item.

In some instances, a resource of a resource server 104 may include asearch engine feature. The search engine feature may receive a searchquery (e.g., a string of text) via an input feature (an input text box,etc.). The search engine may search an index of documents (e.g., otherresources, such as webpages, etc.) for relevant search results based onthe search query. The search results may be transmitted as a secondresource to present the relevant search results, such as a search resultwebpage, on a display of a client device 110. The search results mayinclude webpage titles, hyperlinks, etc. One or more third-party contentitems may also be presented with the search results in a content itemslot of the search result webpage. Accordingly, the resource server 104and/or the client device 110 may request one or more content items fromthe content item selection system 108 to be presented in the contentitem slot of the search result webpage. The content item request mayinclude additional information, such as the client device information,the resource information, a quantity of content items, a format for thecontent items, the search query string, keywords of the search querystring, information related to the query (e.g., geographic locationinformation and/or temporal information), etc. In some implementations,a delineation may be made between the search results and the third-partycontent items to avert confusion.

In some implementations, the third-party content provider may manage theselection and serving of content items by content item selection system108. For example, the third-party content provider may set bid valuesand/or selection criteria via a user interface that may include one ormore content item conditions or constraints regarding the serving ofcontent items. A third-party content provider may specify that a contentitem and/or a set of content items should be selected and served forclient devices 110 having device identifiers associated with a certaingeographic location or region, a certain language, a certain operatingsystem, a certain web browser, etc. In another implementation, thethird-party content provider may specify that a content item or set ofcontent items should be selected and served when the resource, such as awebpage, document, etc., contains content that matches or is related tocertain keywords, phrases, etc. The third-party content provider may seta single bid value for several content items, set bid values for subsetsof content items, and/or set bid values for each content item. Thethird-party content provider may also set the types of bid values, suchas bids based on whether a user clicks on the third-party content item,whether a user performs a specific action based on the presentation ofthe third-party content item, whether the third-party content item isselected and served, and/or other types of bids.

While the foregoing has provided an overview of a system 100 forselecting and serving content items to client devices 110, examples ofcontent items served with resources will now be described in referenceto FIGS. 2A-3B. FIG. 2A depicts an example display 200 (shown inphantom) of a client device, such as client device 110 of FIG. 1, with aweb browser 210 for displaying resources on the display 200. The webbrowser 210 may operate by receiving input of a URL in an address bar,such as a web address, from an input device (e.g., a pointing device, akeyboard, a touch screen, or another form of input device). In response,one or more processing modules of a client device executing theinstructions from the web browser 210 may request data from anotherdevice connected to a network, such as network 106, referred to by theURL address (e.g., a resource server 104). The other device may thenprovide data to effect presentation of the resource to the clientdevice, which causes visual indicia to be displayed by the display 200of the client device. Accordingly, the web browser 210 displays aretrieved resource 220, such as a webpage.

An example resource 220 is shown displayed by the display 200 of theclient device using the web browser 210. The resource 220 includes afirst content portion 222 and a second content portion 224. Afirst-party content provider may separate the first content portion 222and the second content portion 224 via a div element. In someimplementations, such as resources implementing responsive web designaspects, the first content portion 222 and the second content portion224 may be defined based on a percentage of a viewport of the device onwhich the resource 220 is to be displayed. The viewport is the area thatis visible within the browser 210 or other application when displayingthe resource 220. The first content portion 222 and/or the secondcontent portion 224 may include first-party content 226 of thefirst-party content provider, such as a news article, a social networkinterface, an application, etc. The resource 220 may also include codeto request one or more third-party content items, such as third partycontent item 228, to be presented with the first-party content 226. Inthe implementation shown in FIG. 2A, a third-party content item 228 isshown served in the second content portion 224, such as through the useof content item selection system 108 of FIG. 1. The first-party contentprovider may include code to identify all or a portion of the secondcontent portion 224 where the third-party content item 228 will beshown. For example, the first-party content provider may insert a pieceof code, such as “ins class=‘contentitem’/ins” at each point where athird-party content item is to be presented. In other implementations,elements other than an insert element may be used, such as a divelement, “div class=‘contentitem’/div.” In addition, the cascading stylesheet (CSS) class may have a label other than “contentitem.” As will bedescribed in greater detail below, an asynchronous tag may be includedto request a script, such as JavaScript®, when the resource 220 is to berendered on the client device. The script is configured to automaticallydetermine a size for a content item to be presented with the resource220 based on a type of the client device, a screen size of the clientdevice, the viewport size, and/or the size of a parent element (e.g.,second content portion 224) such that a request sent to the content itemselection system results in an appropriately sized content item for theresource 220 presented on the display 200 of the client device.

FIG. 2B depicts the display 200 of FIG. 2A showing the web browser 210resized such that the resource 220 is also resized, such as throughresponsive web page design. The script may be configured toautomatically determine a new size for the third-party content itembased on the resizing of the resource 220. In some implementations, thenew size for the third-party content item 228 may be the same such thatthe third-party content item 228 may simply remain presented. Ininstances where the new size is different, a third-party content item230 of the corresponding new size may be requested from the content itemselection system to be displayed with the resource 220 or the previouslyserved third-party content item 228 may be resized at the client devicewithout a request to the content item selection system (e.g., viaseam-carving, stretching, etc.). In some implementations, thethird-party content item 230 may be the same as third-party content item228, only in a different size.

FIG. 3A depicts a mobile client device 300, such as a smartphone ortablet, on which a resource 320 may be displayed by a display 302 of theclient device 300. In the implementation show, a web browser 310 isexecuting on the module client device 300 for displaying resources 320on the display 302. The web browser 310 may operate by receiving inputof a URL in an address bar, such as a web address, from an input device(e.g., a pointing device, a keyboard, a touch screen, or another form ofinput device). In response, one or more processing modules of the clientdevice 300 executing the instructions from the web browser 310 mayrequest data from another device connected to a network, such as network106, referred to by the URL address (e.g., a resource server 104). Theother device may then provide data to effect presentation of theresource 320 to the client device 300, which causes visual indicia to bedisplayed by the display 302 of the client device 300. Accordingly, theweb browser 310 displays a retrieved resource 320, such as a webpage.

An example resource 320 is shown displayed by the display 302 of theclient device 300 using the web browser 310. The resource 320 includes afirst content portion 322 and a second content portion 324. Afirst-party content provider may separate the first content portion 322and the second content portion 324 via a div element. In someimplementations, such as resources implementing responsive web designaspects, the first content portion 322 and the second content portion324 may be defined based on a percentage of a viewport of the device 300on which the resource 320 is to be displayed. The first content portion322 and/or the second content portion 324 includes the first-partycontent 326 of the first-party content provider, such as a news article,a social network interface, an application, etc. The resource 320 mayalso include code to request one or more third-party content items, suchas third-party content item 328, to be presented with the first-partycontent 326. In the implementation shown in FIG. 3A, a third-partycontent item 328 is shown served in the second content portion 324, suchas through the use of content item selection system 108 of FIG. 1. Thefirst-party content provider may include code to identify all or aportion of the second content portion 324 where the third-party contentitem 328 will be shown. For example, the first-party content providermay insert a piece of code, such as “ins class=‘contentitem’/ins” ateach point where a third-party content item 328 is to be presented. Inother implementations, elements other than an insert element may beused, such as a div element, “div class=‘contentitem’/div.” In addition,the cascading style sheet (CSS) class may have a label other than“contentitem.” As will be described in greater detail below, the classmay include an asynchronous tag to request a script, such asJavaScript®, when the resource 320 is to be rendered on the clientdevice 300. The script is configured to automatically determine the sizefor a content item to be presented with the resource 320 based on a typeof the client device 300, a screen size of the client device 300, theviewport size, and/or the size of a parent element (e.g., second contentportion 324) such that a request sent to the content item selectionsystem results in an appropriately sized content item for the resource320 presented on the display 302 of the client device 300.

FIG. 3B depicts the device 300 of FIG. 3A rotated such that the resource320 presented on the display 302 of the device 300 is rotated from aportrait orientation to a landscape orientation. In some instances, theorientation change for the resource 320 may result in the resource 320being presented with a different configuration or sizing. The script maybe configured to automatically determine a new size for the third-partycontent item based on the different configuration or sizing of theresource 320. In some implementations, the new size for the third-partycontent item 328 may be the same such that the third-party content item328 may simply remain presented. In instances where the new size isdifferent, a third-party content item 330 of the corresponding new sizemay be requested from the content item selection system to be displayedwith the resource 320 or the previously served third-party content item328 may be resized at the client device 300 without a request to thecontent item selection system (e.g., via seam-carving, stretching,etc.). In some implementations, the third-party content item 330 may bethe same as third-party content item 328, only in a different size. Asmay be appreciated, the sizing for the third-party content item may bedetermined automatically such that the owner or creator of the resource220, 320 may not need to determine the right size for a third-partycontent item for various sizes or configurations of the resource 220,320.

The CSS classes described above, such as ‘contentiem,’ may include anasynchronous tag that requests a script. The asynchronous tag may be atag, such as:

script async

src=“/pagead/js/contentitemjs”/script

ins class=“contentitem” data-ad-client=“ca-pub-1234”data-ad-slot=“my-slot”/ins script(content item=window.content item∥[]).push({ }); /script

that is inserted into a portion of the resource where a third-partycontent item is to be displayed. In some implementations, the tag may befurther configured to limit the geometric types of third-party contentitems that may be selected. For example, the tag may include a value orvalues for a variable that limits the geometric types of third-partycontent items that may be selected, such as a variable named“data-ad-format,”. Such geometric types may include horizontal,vertical, rectangle, etc. Thus, including the variable ofdata-ad-format=“horizontal,vertical” in the tag results in onlyhorizontal and vertical content item sizes being eligible for selectionfor that tag. If data-ad-format is omitted, then any geometric type ofcontent item may be selected.

When the script, such as contentitemjs, is received and executed by theclient device, the script may be configured to locate all the portionsof the resource where third-party content items will be served and asize determination is needed (e.g., where ins class=‘contentitem’/ins ordiv class=‘contentitem’/div are located), determine a size of aviewport, determine a width of a parent element for each portion where athird-party content item will be served, and determine a content itemsize for each portion where third-party content items will be served. Insome implementations, the script may be triggered to be executed basedon a DOMContentLoaded event such that there is enough information aboutthe various sizes of the elements of the resource even if all theelements of the resource have not necessarily finished loading. Thus,the script can determine an appropriate size for the third-party contentitem for resources that are rendered differently based on the clientdevice, such as web pages implementing responsive web page design. Thedetermination of the content item size may be based, at least in part,on the size of the viewport and the width of a parent element of theresource, as will be described in greater detail herein. The script maybe configured to query the document object model (DOM) to find theparent element of the where ins class=‘contentitem’/ins or divclass=‘contentitem’/div is located and query the DOM for the width ofthe parent element. In some implementations, the height of the parentelement may also be used in the determination of the content item size.

The content item size determination may include selecting a predeterminestandard size, such as a standard size specified by the InteractiveAdvertising Bureau (IAB). Such standard sizes may include 320 px by 50px, 234 px by 60 px, 468 px by 60 px, 728 px by 90 px, 970 px by 90 px,125 px by 125 px, 180 px by 150 px, 200 px by 200 px, 250 px by 250 px,300 px by 250 px, 336 px by 280 px, 120 px by 600 px, 160 px by 600 px,300 px by 600 px, and/or any other standard content item size. As willbe described in greater detail herein, the set of standard sizes may beranked and the highest ranked standard size may be selected.

In some implementations, the set of standard sizes that may be eligiblefor ranking may be subject to additional limitations. For example, astandard size may not be ranked if the area of the standard size exceedsa threshold value for a predetermined percentage of a viewport area. Thethreshold value may be a value between 10%, inclusive, to 50%,inclusive. In one implementation the threshold value may be 15%. Inother implementations, the first-party content provider may specify thethreshold value. Other limitations to the inclusion of a standardcontent item size in the ranking may be whether the width of thestandard content item size exceeds a width of the viewport, whether theheight of the standard content item size exceeds a height of theviewport, and/or whether the standard content item size is an excludedgeometric type based on the value or values of the variable ofdata-ad-format.

Once the set of eligible standard content item sizes is determined, eachstandard content item size of the set of standard content item sizes maybe ranked. The ranking may be based, at least in part, on an area ofeach predetermined standard content item size, an estimated revenuevalue of each predetermined standard content item size, and/or a ratiomatch value. In some implementations, the rating for each standardcontent item size may be based on the equation:Rating=Area*eRPM*ratio matchIn some implementations, each multiplier in the foregoing equation maybe weighted. The area of each predetermined standard content item sizemay be the pixel area of the predetermined standard content item size,such as 320 px by 50 px, which has an area of 16,000 pixels. Theestimated revenue value for a predetermined standard content item size(i.e., estimated revenue per thousand impressions or eRPM in theequation above) may be a value determined for each predeterminedstandard content item size based on global data for that particularpredetermined standard content item size. That is, a list of staticvalues for each standard content item size may be used based onhistorical data. In other implementations, the estimated revenue valuefor a predetermined standard content item size may a value that ispublisher-specific, website specific, webpage specific, and/orlocation-specific.

The ratio match value provides a measure of how well suited thepredetermined standard content item size is for the portion of theresource where a third-party content item will be served. The ratiomatch value may be based on a width of a parent element and a width ofthe viewport. In brief, vertical standard content item sizes may bepreferable to be displayed in narrow columnar portions of the displayedresource, horizontal standard content item sizes may be preferable to bedisplayed in wide portions of the displayed resource, and rectangularstandard content item sizes may be preferable to be displayed in theremaining portions of the displayed resource. In an implementation, anif-then statement may be used to sort standard content item sizes basedon the ratio match value. For example:

if width of parent element <=25% of width of body:

favor vertical, then square, then horizontal

else if width of parent element <=50% of width of body:

favor square then horizontal then vertical

else:

favor horizontal then square then vertical.

Another implementation may determine a value for the ratio match valuebased on a percentage of a width of a parent element that the standardcontent item size would occupy. For example, FIG. 4 is an illustrationof an implementation of a first-party resource 400 shown in a viewport402. The resource 400 includes multiple divisions of elements 404, 406,408, 410 and showing an example third-party content item 420 having astandard content item size of 728 pixels by 90 pixels in a parentelement 410. The parent element 410 has a width of 800 pixels and spansacross the entire width of the viewport 402. For a set of standardcontent item sizes, such as those enumerated above, the standard contentitem size that does not exceed the width of the parent element 410 andoccupies the highest percentage of the width of the parent element 410is the standard content item size of 728 pixels by 90 pixels; an examplethird-party content item 420 of this size is shown within the parentelement 410. Thus, the ratio match value for the standard content itemsize of 728 px by 90 px may be determined to be 728 divided by 800, or0.91 or 91%. The ratio match value may be used in the rating equationdescribed above to determine a rating for the standard content item sizesuch that a standard content item size with the best rating may bedetermined and selected. The other standard content item sizes may alsohave ratio match values determined in a similar manner.

Another implementation may determine the ratio match value based on apercentage of a width of a parent element that the standard content itemsize would occupy and a percentage of a remaining portion of a viewportwidth that a height dimension of the standard content item size wouldoccupy. FIG. 5A is an illustration of an implementation of a first-partyresource 500 shown in a viewport 502. The resource 500 includes multipledivisions of elements 504, 506, 508, 510 and showing an examplethird-party content item 520 having a standard content item size of 320pixels by 50 pixels in a parent element 510. The parent element 510 hasa width of 320 pixels and spans 25% of the width of the viewport 502.For the standard content item size of the content item 520, thepercentage of the width of the parent element 510 that the standardcontent item size occupies is 100% (i.e., 320 px divided by 320 px isone). However, as shown in FIGS. 5A-5B, the standard content item sizeof 320 pixels by 50 pixels occupies very little vertical space of theparent element 510. Accordingly, a second percentage may be calculatedbased on a remaining portion of the viewport 502 width (i.e., aftersubtracting the width of the parent element 510 from the total width ofthe viewport 502) and a height dimension of the standard content itemsize, shown in FIG. 5B. The width of the remaining portion of theviewport 502 in the example shown is 880 pixels (1200 pixels minus 320pixels). The percentage of the height dimension of the standard contentitem size relative to the width of the remaining portion of the viewport502 is 50 divided by 880, or approximately 6%. Thus, the ratio matchvalue for the standard content item size of 320 pixels by 50 pixels forthe parent element 510 may be the first percentage, 100% or 1.0,multiplied by the second percentage, 6% or 0.06, resulting in a ratiomatch value of 0.06.

In contrast, for a standard content item size of 300 pixels by 600pixels for a third-party content item to be displayed in the parentelement 510, the first percentage is approximately 94% (300 pixel widthfor the standard content item size divided by 320 pixel width for theparent element 510) and the second percentage is approximately 68% (600pixel height for the standard content item size divided by 880 pixelwidth of the remaining portion of the viewport 502). Accordingly, theratio match value for the standard content item size of 300 pixels by600 pixels may be 0.94 multiplied by 0.68, or approximately 0.64. As maybe appreciated, the standard content item size of 300 pixels by 600pixels has a greater ratio match value than the standard content itemsize of 320 pixels by 50 pixels, which indicates that the standardcontent item size of 300 pixels by 600 pixels is likely to be bettersuited for portion of the resource where a third-party content item willbe served.

In some implementations, a multiplier may be used with the secondpercentage of the ratio match value. For example, for a verticalstandard content item size, such as 120 px by 600 px, 160 px by 600 px,or 300 px by 600 px, a multiplier for the second percentage may be zerosince the vertical format may be out of proportion relative to the restof the resource. The multiplier for horizontal or rectangular standardcontent item sizes, such as 320 px by 50 px, 234 px by 60 px, 468 px by60 px, 728 px by 90 px, 970 px by 90 px, 125 px by 125 px, 180 px by 150px, 200 px by 200 px, 250 px by 250 px, 300 px by 250 px, or 336 px by280 px, may be between 1, inclusive, and 2, inclusive. In someimplementations, the multiplier for horizontal standard content itemsizes, such as 320 px by 50 px, 234 px by 60 px, 468 px by 60 px, 728 pxby 90 px, or 970 px by 90 px, may be 1 and the multiplier forrectangular standard content item sizes, such as 125 px by 125 px, 180px by 150 px, 200 px by 200 px, 250 px by 250 px, 300 px by 250 px, or336 px by 280 px, may be 1.5.

Once each eligible standard content item size of the set of standardcontent item sizes is ranked, then the top ranked standard content itemsize may be determined. The height value of the determined standardcontent item size and the width of the parent element are sent to thecontent item selection system, such as part of a content item request.In the implementation shown in FIG. 4, the height value is set to 90pixels, which is the height of the determined standard content itemsize, and the width value is set to 800 pixels, which is the width ofthe parent element 410. The full width of the parent element 410 is sentsuch that, if a textual third-party content item is selected by thecontent item selection system, then the full width of the parent element410 may be used for displaying the textual content item. If an imagethird-party content item is selected by the content item selectionsystem then the standard content item size may be used. Data to effectdisplay of the selected content item may be transmitted to the clientdevice such that the selected content item is displayed with theresource.

In some implementations, further limits may be applied during theselection of content item sizes. For example, a total limit thresholdvalue may be used such that the total area of all the content item sizesdoes not exceed a predetermined percentage of the viewport area or atotal limit threshold value may be used such that the total area of thecontent item sizes above the fold do not exceed a predeterminedpercentage of the viewport area.

FIG. 6 depicts an example flow diagram of a process 600 that may beimplemented by a client device, such as client device 110 of FIG. 1, toautomatically determine a size for a content item based on a parentelement. The process 600 includes receiving data to effect presentationof a requested resource (block 602). The client device may request thedata to effect presentation of a resource via a user entering a URL intoan address portion of a web browser. A resource server, such as resourceserver 104 of FIG. 1, sends the data to effect presentation of theresource to the client device via network 106.

The process 600 further includes receiving a script (block 604). In someimplementations the script may be requested and received from anotherdevice, such as the content item selection system 108 of FIG. 1 oranother device. In some other implementations, the script may be cachedon the client device and retrieved and executed.

The script is configured to cause the client device to locate theportions of the resource where third-party content items will be servedand a size determination is needed (block 606). The locating of theportions of the resource where third-party content items will be servedand a size determination is needed may include identifying the portionsof the resource having an insert element for “insclass=‘contentitem’/ins”. In other implementations, other identifiers toindicate the locations in the resource where third-party content itemswill be served and a size determination is needed may be used, such as“div class=‘contentitem’/div”.

The script is further configured to cause the client device to determinea size of a viewport (block 608). In some implementations, thedetermination of the size of the viewport may include retrieving thevalues for body offsetWidth and body offsetHeight for the width andheight of the body of the resource. The script is further configured tocause the client device to determine a width of a parent element foreach portion where a third-party content item will be served (block610). For example, the determination of the parent element width may bedetermined based on the viewport width, a parent element of the parentelement, a static value for the parent element width, etc. In someimplementations, the script may be configured to query the DOM to findthe parent element of the where ins class=‘contentitem’/ins or divclass=‘contentitem’/div is located and query the DOM for the width ofthe parent element. The height of the parent element may also be queriedand used in the determination of the content item size.

The script is further configured to cause the client device to determinea content item size for each portion where third-party content itemswill be served (block 612). The determination of the content item sizemay be based, at least in part, on the size of the viewport and thewidth of a parent element of the resource, as described in greaterdetail herein. In some implementations, the height of the parent elementmay also be used in the determination of the content item size. Thecontent item size determination may include selecting a predeterminestandard content item size based on a ranking of each predeterminedstandard content item size. As noted above, the set of standard sizesthat may be eligible for ranking may be subject to additionallimitations in some implementations. For example, a predeterminedstandard content item size may not be ranked if the standard sizeexceeds a threshold value for a predetermined percentage of a viewportarea, such as a threshold value of 15% of the area of the viewport. Apredetermined standard content item size may also not be ranked if thewidth of the standard size exceeds the width of the parent elementand/or the height of the standard size exceeds the height of the parentelement. Once the set of eligible standard content item sizes isdetermined, each standard content item size of the set of standardcontent item sizes may be ranked. The ranking may be based, at least inpart, on an area of each predetermined standard content item size, anestimated revenue value of each predetermined standard content itemsize, and/or a ratio match value. In some implementations, the ratingfor each standard content item size may be based on the equation:Rating=Area*eRPM*ratio matchIn some implementations, each multiplier in the equation may beweighted. The area of each predetermined standard content item size maybe the pixel area of the predetermined standard content item size. Theestimated revenue value for a predetermined standard content item size(i.e., estimated revenue per thousand impressions or eRPM in theequation above) may be a value determined for each predeterminedstandard content item size based on global data for that particularpredetermined standard content item size. In other implementations, theestimated revenue value for a predetermined standard content item sizemay a value that is publisher-specific, website specific, webpagespecific, and/or location-specific.

The ratio match value may be based, at least in part, on the width ofthe parent element and a width of the viewport. In some implementations,the ratio match value for each predetermined standard content item sizemay be based, at least in part, on a ratio of a first dimension of thestandard content item size, such as a width dimension, to the width ofthe parent element. In a further implementation, the ratio match valuefor each predetermined standard content item size may be based, at leastin part on a ratio of a second dimension of each standard content itemsize, such as a height dimension, to the width of the viewport less thewidth of the parent element. Once each eligible standard content itemsize of the set of standard content item sizes is ranked, then the topranked standard content item size may be determined.

A content item may be requested by the client device from a content itemselection system (block 614) for each portion of the resource needing athird-party content item. The content item request may include theheight value of the determined standard content item size and the widthvalue of the parent element. In other implementations, the content itemrequest may include the height value and the width value of thedetermined standard content item size. The request may be in the form ofa content item request URL. In some implementations, device and/or theresource information or parameters may also be included with the contentitem request, such as appended to a content item request URL (e.g.,/page/contentitem?devid=abc123&devnfo=A34r0).

A content item served in response to the content item request may bedisplayed with the resource (block 616). The client device may receivedata to effect display of a served content item from a content itemselection system. Using the received data, the client device may displaythe served content item with the resource.

In some implementations, the process 600 may determine a second contentitem size based on a second size of the viewport and/or a second widthof the parent element (block 608, 610, 612). For example, as shown inFIGS. 2B and 3B, a resource may be modified or resized in response to areduction in size to a web browser window or an orientation change of amobile device or tablet. The script may be configured to query the DOMto find the parent element of the where ins class=‘contentitem’/ins ordiv class=‘contentitem’/div is located and query the DOM for the newwidth of the parent element. The new height of the parent element mayalso be queried and used in the determination of the second content itemsize. In some instances, the client device may request a second contentitem from the content item selection system (block 614) and display theserved second content item with the resource (block 616). In otherimplementations, the script may be configured to cause the client deviceto resize the originally served content item based on the determinedsecond content item size (e.g., via seam carving, stretching, etc.). Insome implementations, the served second content item may be the same asprevious served content item but having a size according to thedetermined second content item size.

FIG. 7 depicts an example flow diagram of a process 700 that may beimplemented by a content item selection system, such as content itemselection system 108 of FIG. 1, to select and serve a content item basedon an automatic determination of a size for the content item. Theprocess 700 includes serving a script to a client device in response toa request (block 702). The script is configured to cause the clientdevice to perform several operations described herein, including one ormore of the operations described in reference to blocks 606, 608, 610,612 of FIG. 6. For example, the script may be configured to cause theclient device to cause the client device to locate the portions of theresource where third-party content items will be served and a sizedetermination is needed, determine a size of a viewport, determine awidth of a parent element for each portion where a third-party contentitem will be served, and/or determine a content item size for eachportion where third-party content items will be serve. In someimplementations, the height of the parent element may also be used inthe determination of the content item size.

The determination of the content item size may be based, at least inpart, on the size of the viewport and the width of a parent element ofthe resource, as described in greater detail herein. The content itemsize determination may include selecting a predetermine standard contentitem size based on a ranking of each predetermined standard content itemsize. The set of standard sizes that may be eligible for ranking may besubject to additional limitations in some implementations. For example,a predetermined standard content item size may not be ranked if thestandard size exceeds a threshold value for a predetermined percentageof a viewport area, such as a threshold value of 15% of the area of theviewport. Once the set of eligible standard content item sizes isdetermined, each standard content item size of the set of standardcontent item sizes may be ranked. The ranking may be based, at least inpart, on an area of each predetermined standard content item size, anestimated revenue value of each predetermined standard content itemsize, and/or a ratio match value. In some implementations, the ratingfor each standard content item size may be based on the equation:Rating=Area*eRPM*ratio matchIn some implementations, each multiplier in the equation may beweighted. The area of each predetermined standard content item size maybe the pixel area of the predetermined standard content item size. Theestimated revenue value for a predetermined standard content item size(i.e., estimated revenue per thousand impressions or eRPM in theequation above) may be a value determined for each predeterminedstandard content item size based on global data for that particularpredetermined standard content item size. In other implementations, theestimated revenue value for a predetermined standard content item sizemay a value that is publisher-specific, website specific, webpagespecific, and/or location-specific.

The ratio match value may be based, at least in part, on the width ofthe parent element and a width of the viewport. In some implementations,the ratio match value for each predetermined standard content item sizemay be further based, at least in part, on a ratio of a first dimensionof the standard content item size, such as a width dimension, to thewidth of the parent element. In a further implementation, the ratiomatch value for each predetermined standard content item size may bebased, at least in part on a ratio of a second dimension of eachstandard content item size, such as a height dimension, to the width ofthe viewport less the width of the parent element. Once each eligiblestandard content item size of the set of standard content item sizes isranked, then the top ranked standard content item size may be determinedby the client device. In some implementations, the script may be furtherconfigured to ease the transition display of the resource once thecontent item size is determined. For example, the script may include“transition: height 0.5 s ease-out;” to cause the client device to easethe height out to the height of the determine content item size overhalf a second to smoothly expand the resource displayed on a display ofthe client device.

A dimension, such as a height or a width, of the determined content itemsize may be received (block 704). The dimension of the determinedcontent item size may be received as part of a content item request froma client device. The content item request may also include a dimensionof the parent element, such as a width value or a height value. In oneimplementation, the content item request may include the height value ofthe determined standard content item size and the width value of theparent element. The request may be in the form of a content item requestURL. In some implementations, device and/or the resource information orparameters may also be included with the content item request, such asappended to a content item request URL (e.g.,/page/contentitem?devid=abc123&devnfo=A34r0).

A set of content items may be determined based, at least in part, on thereceived dimension of the determined content item size (block 706). Insome implementations, image content items having a content item sizecorresponding to the determined content item size, based on the receiveddimension, may be included in the set of content items for an auction tobe performed by the content item selection system. The set of contentitems may also include textual content items or other content items. Acontent item may be selected (block 708) based, at least in part, on anauction performed by the content item selection system. The selection ofthe content item may be based on a bid associated with each content itemof the set of content items in the auction. In some implementations, ascore may be generated for each content item of the set of content itemsin the auction and the score may be used to rank each content item ofthe set of content items. A content item may be selected based on therank by the content item selection system.

Data to effect display of the selected content item in a parent elementof a resource (block 710). The data may be transmitted from the contentitem selection system 108 to a client device 110 and/or resource server104 via the network 106.

In some implementations, the process 700 may receive a dimension of asecond content item size based on a second size of the viewport and/or asecond width of the parent element as determined by the script, such asthat described in reference to blocks 608, 610, 612 of FIG. 6. Forexample, as shown in FIGS. 2B and 3B, a resource may be modified orresized in response to a reduction in size to a web browser window or anorientation change of a mobile device or tablet. In some instances theprocess 700 may further include receiving a dimension of the determinedsecond content item size and serving second data to the client device toeffect display of the selected content item with the resource based onthe dimension of the determined second content item size. In otherimplementations, the script may be configured to cause the client deviceto resize the originally served content item based on the determinedsecond content item size (e.g., via seam carving, stretching, etc.).

In some implementations, the dimensions of the determined content itemsize included in the content item request may be stored in a database ofthe content item selection system or another system. The dimensions ofthe served content item may also be stored in the database. In addition,any specific requested shapes, e.g., vertical, horizontal, and/orrectangular, may be stored in the database. The requested dimensions andserved dimensions may be integer widths and heights. The requestedshapes may be defined as an enum. The stored requested dimensions,served dimensions, and/or the requested shapes may be used to generatereporting data, such as numerical data or a visualization. The requestedwidth dimensions may be bucketized into buckets such as <120 px, >=120px<125 px, >=125 px<160 px, >=160 px<180 px, >=180 px<200 px, >=200px<234 px, >=234 px<250 px, >=250 px<300 px, >=300 px<320 px, >=320px<336 px, >=336 px<468 px, >=468 px<728 px, >=728 px<970 px,and/or >=970 px. Thus, statistical data may be generated for afirst-party content provider of a resource regarding the performance ofvarious sized content items and/or for a third-party content providerregarding the performance of their various sized content items.

In some implementations, one or more operations of the script may beperformed by the content item selection system. For example, the scriptmay be configured to output the viewport size and the parent elementwidth to the content item selection system and the content itemselection system may be configured to determine the content item size,determine a set of content items based on the determined content itemsize, select a content item, and serve the selected content item to theclient device to be displayed in the parent element with the resource.

FIG. 8 is a block diagram of a computer system 800 that can be used toimplement the client device 110, content item selection system 108,third-party content server 102, resource server 104, etc. The computingsystem 800 includes a bus 805 or other communication component forcommunicating information and a processor 810 or processing modulecoupled to the bus 805 for processing information. The computing system800 can also include one or more processors 810 or processing modulescoupled to the bus for processing information. The computing system 800also includes main memory 815, such as a RAM or other dynamic storagedevice, coupled to the bus 805 for storing information, and instructionsto be executed by the processor 810. Main memory 815 can also be usedfor storing position information, temporary variables, or otherintermediate information during execution of instructions by theprocessor 810. The computing system 800 may further include a ROM 820 orother static storage device coupled to the bus 805 for storing staticinformation and instructions for the processor 810. A storage device825, such as a solid state device, magnetic disk or optical disk, iscoupled to the bus 805 for persistently storing information andinstructions. Computing device 800 may include, but is not limited to,digital computers, such as laptops, desktops, workstations, personaldigital assistants, servers, blade servers, mainframes, cellulartelephones, smart phones, mobile computing devices (e.g., a notepad,e-reader, etc.) etc.

The computing system 800 may be coupled via the bus 805 to a display835, such as a Liquid Crystal Display (LCD), Thin-Film-Transistor LCD(TFT), an Organic Light Emitting Diode (OLED) display, LED display,Electronic Paper display, Plasma Display Panel (PDP), and/or otherdisplay, etc., for displaying information to a user. An input device830, such as a keyboard including alphanumeric and other keys, may becoupled to the bus 805 for communicating information and commandselections to the processor 810. In another implementation, the inputdevice 830 may be integrated with the display 835, such as in a touchscreen display. The input device 830 can include a cursor control, suchas a mouse, a trackball, or cursor direction keys, for communicatingdirection information and command selections to the processor 810 andfor controlling cursor movement on the display 835.

According to various implementations, the processes and/or methodsdescribed herein can be implemented by the computing system 800 inresponse to the processor 810 executing an arrangement of instructionscontained in main memory 815. Such instructions can be read into mainmemory 815 from another computer-readable medium, such as the storagedevice 825. Execution of the arrangement of instructions contained inmain memory 815 causes the computing system 800 to perform theillustrative processes and/or method steps described herein. One or moreprocessors in a multi-processing arrangement may also be employed toexecute the instructions contained in main memory 815. In alternativeimplementations, hard-wired circuitry may be used in place of or incombination with software instructions to effect illustrativeimplementations. Thus, implementations are not limited to any specificcombination of hardware circuitry and software.

Although an implementation of a computing system 800 has been describedin FIG. 8, implementations of the subject matter and the functionaloperations described in this specification can be implemented in othertypes of digital electronic circuitry, or in computer software,firmware, or hardware, including the structures disclosed in thisspecification and their structural equivalents, or in combinations ofone or more of them.

Implementations of the subject matter and the operations described inthis specification can be implemented in digital electronic circuitry,or in computer software embodied on a tangible medium, firmware, orhardware, including the structures disclosed in this specification andtheir structural equivalents, or in combinations of one or more of them.The subject matter described in this specification can be implemented asone or more computer programs, i.e., one or more modules of computerprogram instructions, encoded on one or more computer storage media forexecution by, or to control the operation of, data processing apparatus.Alternatively or in addition, the program instructions can be encoded onan artificially generated propagated signal, e.g., a machine-generatedelectrical, optical, or electromagnetic signal that is generated toencode information for transmission to suitable receiver apparatus forexecution by a data processing apparatus. A computer storage medium canbe, or be included in, a computer-readable storage device, acomputer-readable storage substrate, a random or serial access memoryarray or device, or a combination of one or more of them. Moreover,while a computer storage medium is not a propagated signal, a computerstorage medium can be a source or destination of computer programinstructions encoded in an artificially generated propagated signal. Thecomputer storage medium can also be, or be included in, one or moreseparate components or media (e.g., multiple CDs, disks, or otherstorage devices). Accordingly, the computer storage medium is bothtangible and non-transitory.

The operations described in this specification can be performed by adata processing apparatus on data stored on one or morecomputer-readable storage devices or received from other sources.

The terms “data processing apparatus,” “computing device,” “processingcircuit,” or “processing module” encompass all kinds of apparatus,devices, and machines for processing data, including by way of example aprogrammable processor, a computer, a system on a chip, or multipleones, a portion of a programmed processor, or combinations of theforegoing. The apparatus can include special purpose logic circuitry,e.g., an FPGA or an ASIC. The apparatus can also include, in addition tohardware, code that creates an execution environment for the computerprogram in question, e.g., code that constitutes processor firmware, aprotocol stack, a database management system, an operating system, across-platform runtime environment, a virtual machine, or a combinationof one or more of them. The apparatus and execution environment canrealize various different computing model infrastructures, such as webservices, distributed computing and grid computing infrastructures.

A computer program (also known as a program, software, softwareapplication, script, or code) can be written in any form of programminglanguage, including compiled or interpreted languages, declarative orprocedural languages, and it can be deployed in any form, including as astand alone program or as a module, component, subroutine, object, orother unit suitable for use in a computing environment. A computerprogram may, but need not, correspond to a file in a file system. Aprogram can be stored in a portion of a file that holds other programsor data (e.g., one or more scripts stored in a markup languagedocument), in a single file dedicated to the program in question, or inmultiple coordinated files (e.g., files that store one or more modules,sub programs, or portions of code). A computer program can be deployedto be executed on one computer or on multiple computers that are locatedat one site or distributed across multiple sites and interconnected by acommunication network.

Processors suitable for the execution of a computer program include, byway of example, both general and special purpose microprocessors, andany one or more processors of any kind of digital computer. Generally, aprocessor will receive instructions and data from a read only memory ora random access memory or both. The essential elements of a computer area processor for performing actions in accordance with instructions andone or more memory devices for storing instructions and data. Generally,a computer will also include, or be operatively coupled to receive datafrom or transfer data to, or both, one or more mass storage devices forstoring data, e.g., magnetic, magneto optical disks, or optical disks.However, a computer need not have such devices. Moreover, a computer canbe embedded in another device, e.g., a mobile telephone, a personaldigital assistant (PDA), a mobile audio or video player, a game console,a Global Positioning System (GPS) receiver, or a portable storage device(e.g., a universal serial bus (USB) flash drive), to name just a few.Devices suitable for storing computer program instructions and datainclude all forms of non volatile memory, media and memory devices,including by way of example semiconductor memory devices, e.g., EPROM,EEPROM, and flash memory devices; magnetic disks, e.g., internal harddisks or removable disks; magneto optical disks; and CD ROM and DVDdisks. The processor and the memory can be supplemented by, orincorporated in, special purpose logic circuitry.

To provide for interaction with a user, implementations of the subjectmatter described in this specification can be implemented on a computerhaving a display device, e.g., a CRT (cathode ray tube) or LCD monitor,for displaying information to the user and a keyboard and a pointingdevice, e.g., a mouse or a trackball, by which the user can provideinput to the computer. Other kinds of devices can be used to provide forinteraction with a user as well; for example, feedback provided to theuser can be any form of sensory feedback, e.g., visual feedback,auditory feedback, or tactile feedback; and input from the user can bereceived in any form, including acoustic, speech, or tactile input.

While this specification contains many specific implementation details,these should not be construed as limitations on the scope of what may beclaimed, but rather as descriptions of features specific to particularimplementations. Certain features described in this specification in thecontext of separate implementations can also be implemented incombination in a single implementation. Conversely, various featuresdescribed in the context of a single implementation can also beimplemented in multiple implementations separately or in any suitablesubcombination. Moreover, although features may be described above asacting in certain combinations and even initially claimed as such, oneor more features from a claimed combination can in some cases be excisedfrom the combination, and the claimed combination may be directed to asubcombination or variation of a subcombination.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults. In certain circumstances, multitasking and parallel processingmay be advantageous. Moreover, the separation of various systemcomponents in the implementations described above should not beunderstood as requiring such separation in all implementations, and itshould be understood that the described program components and systemscan generally be integrated in a single software product or packagedinto multiple software products embodied on tangible media.

References to “or” may be construed as inclusive so that any termsdescribed using “or” may indicate any of a single, more than one, andall of the described terms.

Thus, particular implementations of the subject matter have beendescribed. Other implementations are within the scope of the followingclaims. In some cases, the actions recited in the claims can beperformed in a different order and still achieve desirable results. Inaddition, the processes depicted in the accompanying figures do notnecessarily require the particular order shown, or sequential order, toachieve desirable results. In certain implementations, multitasking andparallel processing may be advantageous.

The claims should not be read as limited to the described order orelements unless stated to that effect. It should be understood thatvarious changes in form and detail may be made by one of ordinary skillin the art without departing from the spirit and scope of the appendedclaims. All implementations that come within the spirit and scope of thefollowing claims and equivalents thereto are claimed.

What is claimed is:
 1. A method for providing content items, the methodcomprising: receiving, from a client device, a request for a contentitem responsive to a resource loading for display on the client device,the request identifying a dimension of a content item size, the contentitem size determined based on a viewport size of a viewport of anapplication of the client device within which the resource is displayed,a resource dimension of the resource, and a parent dimension of a parentelement of the resource; determining, using the one or more processingmodules, a set of content items based on the dimension of the contentitem size identified by the request, each content item of the set ofcontent items having a size that corresponds to the content item sizeidentified by the request; selecting, using the one or more processingmodules and from the determined set of content items that are determinedbased on the dimension of the content item size identified by therequest, a first content item to be displayed on the client device; andserving, using the one or more processing modules and to the clientdevice, data to effect display of the first content item in the parentelement with the resource.
 2. The method of claim 1, wherein the contentitem size is selected from a set of predetermined standard sizes.
 3. Themethod of claim 1, wherein the data causes the client device to rankeach predetermined standard size of a set of predetermined standardsizes, wherein the ranking is based, at least in part, on an area ofeach predetermined standard size, an estimated revenue value of eachpredetermined standard size, and a ratio match value.
 4. The method ofclaim 3, wherein the ratio match value is based, at least in part, onthe width of the parent element and a width of the viewport.
 5. Themethod of claim 4, wherein the ratio match value is based, at least inpart, on a ratio of a first dimension of each predetermined standardsize to the width of the parent element.
 6. The method of claim 5,wherein the ratio match value is further based, at least in part, on aratio of a second dimension of each predetermined standard size to thewidth of the viewport less the width of the parent element.
 7. Themethod of claim 3, wherein a predetermined standard size of the set ofpredetermined standard sizes is not ranked if an area of thepredetermined standard size exceeds a predetermined percentage of anarea of the viewport.
 8. The method of claim 1, wherein the data causesthe client device to determine a second content item size based, atleast in part, on a second size of the viewport and a second width ofthe parent element.
 9. The method of claim 8 further comprising:receiving, at the one or more processing modules, a dimension of thedetermined second content item size; and serving, using the one or moreprocessing modules, second data to the client device to effect displayof the first content item with the resource based on the dimension ofthe determined second content item size.
 10. The method of claim 8,wherein the data causes the client device to resize the first contentitem based on the determined second content item size.
 11. A system forproviding content items comprising: one or more processing modules; andone or more storage devices storing instructions that, when executed bythe one or more processing modules, cause the one or more processingmodules to perform operations comprising: receiving, from a clientdevice, a request for a script responsive to a resource loading fordisplay on the client, the request identifying a dimension of a contentitem size, the content item size determined based on a viewport size ofa viewport of an application of the client device within which theresource is displayed, a resource dimension of the resource, and aparent dimension of a parent element of the resource; determining a setof content items based on the dimension of the content item sizeidentified by the request, each content item of the set of content itemshaving a size that corresponds to the content item size identified bythe request; selecting, from the determined set of content items thatare determined based on the dimension of the content item sizeidentified by the request, a first content item to be displayed on theclient device; and serving data to effect display of the first contentitem in the parent element with the resource.
 12. The system of claim11, wherein the data causes the client device to rank each predeterminedstandard size of a set of predetermined standard sizes, wherein theranking is based, at least in part, on an area of each predeterminedstandard size, an estimated revenue value of each predetermined standardsize, and a ratio match value.
 13. The system of claim 12, wherein theratio match value is based, at least in part, on a ratio of a firstdimension of each predetermined standard size to the width of the parentelement and a ratio of a second dimension of each predetermined standardsize to the width of the viewport less the width of the parent element.14. The system of claim 11, wherein a predetermined standard size of theset of predetermined standard sizes is not ranked if an area of thepredetermined standard size exceeds a predetermined percentage of anarea of the viewport.
 15. The system of claim 11, wherein the datacauses the client device to determine a second content item size based,at least in part, on a second size of the viewport and a second width ofthe parent element.
 16. The system of claim 15, wherein the one or morestorage devices store instructions that cause the one or more processingmodules to perform operations further comprising: receiving a dimensionof the determined second content item size; and serving second data tothe client device to effect display of the first content item with theresource based on the dimension of the determined second content itemsize.
 17. A non-transitory computer-readable storage device storinginstructions that, when executed by one or more processing modules,cause the one or more processing modules to perform operationscomprising: receiving, from a client device, a request for a contentitem responsive to a resource loading for display on the client, therequest identifying a dimension of a content item size, the content itemsize determined based on a viewport size of a viewport an application ofthe client device within which the resource is displayed, a resourcedimension of the resource, and a parent dimension of a parent element ofthe resource; determining a set of content items based on the dimensionof the content item size identified by the request, each content item ofthe set of content items having a size that corresponds to the contentitem size identified by the request; selecting, from the determined setof content items based on the dimension of the content item sizeidentified by the request, a first content item to be displayed on theclient device; and serving data to effect display of the first contentitem in the parent element with the resource.
 18. The non-transitorycomputer-readable storage device of claim 17, wherein the data causesthe client device to rank each predetermined standard size of a set ofpredetermined standard sizes, wherein the ranking is based, at least inpart, on an area of each predetermined standard size, an estimatedrevenue value of each predetermined standard size, and a ratio matchvalue.
 19. The non-transitory computer-readable storage device of claim18, wherein the ratio match value is based, at least in part, on a ratioof a first dimension of each predetermined standard size to the width ofthe parent element and a ratio of a second dimension of eachpredetermined standard size to the width of the viewport less the widthof the parent element.
 20. The non-transitory computer-readable storagedevice of claim 17, wherein a predetermined standard size of the set ofpredetermined standard sizes is not ranked if an area of thepredetermined standard size exceeds a predetermined percentage of anarea of the viewport.